Computer-based systems and/or computing devices configured for push-based transmissions using the target as a system of record

ABSTRACT

An example method includes receiving user profile configuration information identifying a user and determining a recipient list for push-based information updates. The recipient list comprises a plurality of other computing devices and the recipient list is associated with the user profile configuration information. The method further includes determining an information set or application for the push-based information updates. The method further includes receiving an input comprising a change to the information set or the application. The method further includes running a daemon process as a background process of an operating system of the computing device. The daemon process is configured to monitor the information set or the application for the change and automatically transmit the change directly to the plurality of other computing devices without being received by any intermediate devices so as to push the change upon the receiving of the change to the information set or the application.

COPYRIGHT NOTICE

A portion of the disclosure of this patent document contains materialthat is subject to copyright protection. The copyright owner has noobjection to the facsimile reproduction by anyone of the patent documentor the patent disclosure, as it appears in the Patent and TrademarkOffice patent files or records, but otherwise reserves all copyrightrights whatsoever. The following notice applies to the software and dataas described below and in drawings that form a part of this document:Copyright, Capital One Services, LLC., All Rights Reserved.

FIELD OF TECHNOLOGY

The present disclosure generally relates to improved computer-basedplatforms/systems, improved computing devices/components and/or improvedcomputing objects configured for one or more novel technologicalapplications of push-based transmissions using the target as a system ofrecord.

BACKGROUND OF TECHNOLOGY

A computer network platform/system may include a group of computers(e.g., client devices (e.g., laptops, desktop computers, tablets,smartphone devices, internet of things (IOT) devices, etc.), servers,wireless routers or other networking devices) and other computinghardware devices that are linked together through one or morecommunication channels to facilitate communication and/orresource-sharing, via one or more specifically programmed computingdevices, among a wide range of users.

SUMMARY OF DESCRIBED SUBJECT MATTER

In some embodiments, the present disclosure provides an exemplarytechnically improved computer-based method that includes at least thefollowing steps of receiving, by a processor of a computing device, userprofile configuration information identifying a user. The method furtherincludes determining, by the processor, a recipient list for push-basedinformation updates. The recipient list comprises a plurality of othercomputing devices and the recipient list is associated with the userprofile configuration information. The method further includesdetermining, by the processor, an information set or application for thepush-based information updates. The method further includes receiving,by the processor, an input comprising a change to the information set orthe application. The method further includes running, by the processor,a daemon process as a background process of an operating system of thecomputing device. The daemon process is configured to monitor theinformation set or the application for the change and automaticallytransmit the change directly to the plurality of other computing deviceswithout being received by any intermediate devices so as to push thechange upon the receiving of the change to the information set or theapplication.

In some embodiments, the present disclosure provides an exemplarytechnically improved computer-based system that includes at least thefollowing components a memory, a display, and at least one processor ofa computing device that is coupled to the memory. The at least oneprocessor is configured to receive user profile configurationinformation identifying a user. The at least one processor is furtherconfigured to determine a recipient list for push-based informationupdates. The recipient list comprises a plurality of other computingdevices and the recipient list is associated with the user profileconfiguration information. The at least one processor is furtherconfigured to determine an information set or application for thepush-based information updates. The at least one processor is furtherconfigured to receive an input comprising a change to the informationset or the application. The at least one processor is further configuredto run a daemon process as a background process of an operating systemof the computing device. The daemon process is configured to monitor theinformation set or the application for changes and automatically pushthe change to the information set or the application upon the receivingof the change to the information set or the application.

In some embodiments, the present disclosure provides an exemplarytechnically improved non-transitory computer readable medium havinginstructions stored thereon that, upon execution by a computing device,cause the computing device to perform operations including receivinguser profile configuration information identifying a user. Theoperations further include determining a recipient computing device forpush-based information updates based on the user profile configurationinformation. The recipient computing device is associated with afinancial institution with which the user has an account. The operationsfurther include determining transaction details of a transaction thathas occurred related to the account. The operations further includerunning a daemon process as a background process of an operating systemof the computing device. The daemon process is configured to monitor thecomputing device for transactions that occur and automatically transmitthe transaction details directly to the recipient computing devicewithout being received by any intermediate devices so as to push thetransaction details upon the determining that the transaction hasoccurred. The transaction details comprise information configured forverification of the transaction by the financial institution.

BRIEF DESCRIPTION OF THE DRAWINGS

Various embodiments of the present disclosure can be further explainedwith reference to the attached drawings, wherein like structures arereferred to by like numerals throughout the several views. The drawingsshown are not necessarily to scale, with emphasis instead generallybeing placed upon illustrating the principles of the present disclosure.Therefore, specific structural and functional details disclosed hereinare not to be interpreted as limiting, but merely as a representativebasis for teaching one skilled in the art to variously employ one ormore illustrative embodiments.

FIG. 1 is a block diagram depicting a computer-based system and platformin accordance with one or more embodiments of the present disclosure.

FIG. 2 is a block diagram depicting another computer-based system andplatform in accordance with one or more embodiments of the presentdisclosure.

FIGS. 3 and 4 are diagrams illustrating implementations of cloudcomputing architecture/aspects with respect to which the disclosedtechnology may be specifically configured to operate, in accordance withone or more embodiments of the present disclosure.

FIG. 5 is a flowchart illustrating a process for push-basedtransmissions using the target as a system of record in accordance withone or more embodiments of the present disclosure.

FIG. 6 is a flowchart illustrating another process for push-basedtransmissions using the target as a system of record in accordance withone or more embodiments of the present disclosure.

FIG. 7 is a block diagram of a system with base stations for push-basedtransmissions using the target as a system of record in accordance withone or more embodiments of the present disclosure.

FIG. 8 is a block diagram of a system with wireless access points (WAP)for push-based transmissions using the target as a system of record inaccordance with one or more embodiments of the present disclosure.

FIG. 9 is a block diagram of a system with satellites for push-basedtransmissions using the target as a system of record in accordance withone or more embodiments of the present disclosure.

FIG. 10 is a block diagram of a system with a mesh network of clientdevices for push-based transmissions using the target as a system ofrecord in accordance with one or more embodiments of the presentdisclosure.

DETAILED DESCRIPTION

Various detailed embodiments of the present disclosure, taken inconjunction with the accompanying figures, are disclosed herein;however, it is to be understood that the disclosed embodiments aremerely illustrative. In addition, each of the examples given inconnection with the various embodiments of the present disclosure isintended to be illustrative, and not restrictive.

Throughout the specification, the following terms take the meaningsexplicitly associated herein, unless the context clearly dictatesotherwise. The phrases “in one embodiment” and “in some embodiments” asused herein do not necessarily refer to the same embodiment(s), thoughit may. Furthermore, the phrases “in another embodiment” and “in someother embodiments” as used herein do not necessarily refer to adifferent embodiment, although it may. Thus, as described below, variousembodiments may be readily combined, without departing from the scope orspirit of the present disclosure.

In addition, the term “based on” is not exclusive and allows for beingbased on additional factors not described, unless the context clearlydictates otherwise. In addition, throughout the specification, themeaning of “a,” “an,” and “the” include plural references. The meaningof “in” includes “in” and “on.”

It is understood that at least one aspect/functionality of variousembodiments described herein can be performed in real-time and/ordynamically. As used herein, the term “real-time” is directed to anevent/action that can occur instantaneously or almost instantaneously intime when another event/action has occurred. For example, the “real-timeprocessing,” “real-time computation,” and “real-time execution” allpertain to the performance of a computation during the actual time thatthe related physical process (e.g., a user interacting with anapplication on a mobile device) occurs, in order that results of thecomputation can be used in guiding the physical process.

As used herein, the term “dynamically” and term “automatically,” andtheir logical and/or linguistic relatives and/or derivatives, mean thatcertain events and/or actions can be triggered and/or occur without anyhuman intervention. In some embodiments, events and/or actions inaccordance with the present disclosure can be in real-time and/or basedon a predetermined periodicity of at least one of: nanosecond, severalnanoseconds, millisecond, several milliseconds, second, several seconds,minute, several minutes, hourly, several hours, daily, several days,weekly, monthly, etc.

As used herein, the term “runtime” corresponds to any behavior that isdynamically determined during an execution of a software application orat least a portion of software application.

In some embodiments, exemplary inventive, specially programmed computingsystems/platforms with associated devices are configured to operate inthe distributed network environment, communicating with one another overone or more suitable data communication networks (e.g., the Internet,satellite, etc.) and utilizing one or more suitable data communicationprotocols/modes such as, without limitation, IPX/SPX, X.25, AX.25,AppleTalk™, TCP/IP (e.g., HTTP), Bluetooth™, near-field wirelesscommunication (NFC), RFID, Narrow Band Internet of Things (NBIOT), 3G,4G, 5G, GSM, GPRS, WiFi, WiMax, CDMA, satellite, ZigBee, and othersuitable communication modes.

Described herein are methods, systems, computer readable media, etc. forpush-based transmissions using the target as a system of record. Variousembodiments described herein include technical aspects that reduce thenumber of devices used to distribute changes to information or newinformation generated by a user of a client electronic device. Thevarious embodiments described herein further include technical aspectsthat reduce the number of clicks and/or actions taken by users of clientdevices to distribute changes in information changes to information ornew information generated by a user of a client electronic device.

First, with respect to reducing the number of devices used to distributechanges, a user of a client device may generate new information or maymake changes to existing information (the generation of new informationor changes to existing information may be collectively referred toherein as a change to an information set). That change to theinformation set may be monitored and detected automatically by a processrunning on the client's device (e.g., a background or daemon processrunning as part of an operating system). When the change is detected,the change to that information may be automatically pushed to otherclient devices by the client device on which the change was initiallydetected. The client devices to which the change is pushed may includedevices specified by the user, devices to which the user hascommunicated with in the past, and/or a predefined list of devices.

In some embodiments, the process operating on the client device maydetect the change and transmit it to other devices without the changebeing sent to and/or processed by another device (e.g., an applicationserver). For example, applications on a client device may communicatewith an application server typically, but in various example embodimentsdescribed herein, the changes may not pass through, be communicated to,or otherwise be transmitted to an application server. In this way, thechange to the information may be communicated directly to the otherclient devices without being transmitted to intermediate device(s).However, the client device may, in various embodiments, utilizeintermediate communications infrastructure (e.g., network infrastructuresuch as data lines, wireless access points (WAPs), base stations,data/voice/text switching network infrastructure, other internetcommunications infrastructure, satellite communications infrastructure,etc.).

Some embodiments of non-intermediate device transmission between clientdevices may be configured for distributing updated or new information toa group of client devices (e.g., contacts of a user) without theinvolvement of a backend server or servers, such as an applicationserver. The non-intermediate device transmission may provide a user withmore control over and/or security for their data, as the data isreceived by and/or processed by fewer devices than in systems where abackend server(s) facilitates or otherwise processes informationupdates. By having fewer devices process the information updates, thereare fewer opportunities for the data to be accessed by unauthorizedparties or otherwise be breached, for example. In addition, thetechnical solutions described herein may also provide for more efficientdistribution of information updates. When the information passes throughor is processed by fewer devices, less computing resources may beneeded, and the information may be transmitted and may be received inless time than a system that uses more intermediate devices to process,store, and/or route information.

In addition, the systems and methods described herein may offer othertechnical benefits. For example, various embodiments described hereinmay allow a user to avoid updating other devices individually, such asby sending updated documents, contact information, etc. to other devicesand/or other users manually. With the various embodiments describedherein, such information updates may be monitored for and sent to otherdevices automatically.

Furthermore, the embodiments described herein may use a backgroundprocess to monitor for and send information updates. For example, adaemon process of a device's operating system may monitor forinformation updates and automatically send the updates to other devicesonce the process determines that an information update has occurred. Inthis way, the device may always be running a process to check forinformation updates whenever the device is running without having to runor launch a separate application for monitoring and sending informationupdates. By operating as part of a process of the device's operatingsystem, the process may use less processing power of the device.Similarly, a device that receives the information updates may also berunning a daemon process in the background as part of the device'soperating system. Thus, the receiving device may also receive theinformation updates and update the information set or application towhich the updates apply accordingly without running or launching aseparate application to do so.

Advantageously, the embodiments described herein further ensure thatinformation sets and/or applications are updated. In some embodiments,an information set may include information that may be updated bymultiple different devices (e.g., a contact list may have contactinformation that may be updated by multiple parties related to differentcontact information stored in the contact list). Using the methods andsystems described herein, updates may be pushed from various devices tokeep the contact list up to date, rather than a single device having torequest or pull updates from a plurality of devices.

The embodiments described herein may also reduce the number of clicks,touches, or other interactions taken by a user of a device to receiveand/or send information updates. Such features provide improved ease ofuse for a user and may require less processing to send or receiveinformation updates. For example, automatically determining that aninformation set has changed, pushing the change, and updating theinformation set on the device that received the change may all occurautomatically without interaction from a user. Accordingly, the devicesinvolved may not have to perform any processing related to a useraction, such as displaying prompts to a user on a display, receivingresponses to those prompts, etc. Thus, processing loads on devices maybe reduced, all while improving convenience and ease of use for a user.

The push-based updates described herein therefore solve technologicalproblems with updating information sets or applications stored onmultiple electronic devices, using the technological solutionsnecessarily rooted in computer technology described herein to improvesecurity and/or performance for those devices and the informationexchanged between those devices. As a further example, battery life andusage are common concerns for mobile electronic devices. Using theembodiments described herein, persons using a mobile electronic devicethat monitors for and automatically pushes and receives information willuse less processing power, thereby preserving battery life. Running abackground process to monitor for updates may tax the mobile electronicdevice's processing capabilities and battery life less because aseparate application is not always running and the device does not needto facilitate further user interaction as described herein.

For example, based on at least the problems and solutions describedherein, at least some embodiments of the present disclosure thereforeresult in improved functioning of mobile electronic devices, networkresources, and/or back end servers (including cloud computingresources). For example, according to the various techniques describedherein, a database, lookup table, or similar data structure ofrelationships between a user, their financial account(s), and theirelectronic device(s) (including, e.g., information about how tocommunicate with those devices such as phone numbers, user names,internet protocol (IP) addresses, media access control (MAC) address, orother type of identifying information used to communicate with adevice), as well as other users and their electronic device(s) may beused to facilitate efficient push-based updates of changes toinformation. These stored relationships may facilitate efficient routingand/or execution of sending out those push-based updates. For example, alookup table or database may include the parties or devices to whom aparticular information updates should be sent, how to best route thatinformation update, what communication protocol or network to use tosend that information update, etc.

A lookup table, database, etc. may also include relationships betweenusers. For example, relationships between users may include users whohave one another in their contact lists, have been shared an informationupdate before of a particular type or related to a particularapplication, have been opted into an information sharing relationship bya user, or any other preexisting relationship between users. This lookuptable, database, etc. may be stored on each user's device so that when adaemon process running in an operating system detects a change, thedatabase or lookup table may be referred to in order to determine whatdevices/users to distribute the information update to. Because theserelationships may be pre-established in a database, lookup table, etc.stored in a memory of an electronic device, those relationships can belooked up at later times without taxing computing resources to rebuildor re-determine the relationships each time. This represents ademonstrable technological improvement that allows a user device toquickly and easily send push-based information updates. In other words,the embodiments herein provide for a particular manner of summarizinginformation by and on electronic devices, such that the electronicdevices provide specific manners for pushing updates to a limited set ofusers or devices relevant to a user, rather than using conventionalmethods to send information.

The material disclosed herein may be implemented in software or firmwareor a combination of them or as instructions stored on a machine-readablemedium, which may be read and executed by one or more processors. Amachine-readable medium may include any medium and/or mechanism forstoring or transmitting information in a form readable by a machine(e.g., a computing device). For example, a machine-readable medium mayinclude read only memory (ROM); random access memory (RAM); magneticdisk storage media; optical storage media; flash memory devices;electrical, optical, acoustical or other forms of propagated signals(e.g., carrier waves, infrared signals, digital signals, etc.), andothers.

The aforementioned examples are, of course, illustrative and notrestrictive.

As used herein, the term “user” shall have a meaning of at least oneuser. In some embodiments, the terms “user”, “subscriber” “consumer” or“customer” should be understood to refer to a user of an application orapplications as described herein and/or a consumer of data supplied by adata provider. By way of example, and not limitation, the terms “user”or “subscriber” can refer to a person who receives data provided by thedata or service provider over the Internet in a browser session, or canrefer to an automated software application which receives the data andstores or processes the data.

FIG. 1 is a block diagram depicting a computer-based system and platformin accordance with one or more embodiments of the present disclosure.However, not all of these components may be required to practice one ormore embodiments, and variations in the arrangement and type of thecomponents may be made without departing from the spirit or scope ofvarious embodiments of the present disclosure. In some embodiments, theexemplary inventive computing devices and/or the exemplary inventivecomputing components of the exemplary computer-based system/platform 100may be configured to manage a large number of members and/or concurrenttransactions, as detailed herein. In some embodiments, the exemplarycomputer-based system/platform 100 may be based on a scalable computerand/or network architecture that incorporates varies strategies forassessing the data, caching, searching, and/or database connectionpooling. An example of the scalable architecture is an architecture thatis capable of operating multiple servers.

In some embodiments, referring to FIG. 1, members 102-104 (e.g.,clients) of the exemplary computer-based system/platform 100 may includevirtually any computing device capable of receiving and sending amessage over a network (e.g., cloud network), such as network 105, toand from another computing device, such as servers 106 and 107, eachother, and the like. In some embodiments, the member devices 102-104 maybe personal computers, multiprocessor systems, microprocessor-based orprogrammable consumer electronics, network PCs, and the like. In someembodiments, one or more member devices within member devices 102-104may include computing devices that typically connect using a wirelesscommunications medium such as cell phones, smart phones, pagers, walkietalkies, radio frequency (RF) devices, infrared (IR) devices, CBs,integrated devices combining one or more of the preceding devices, orvirtually any mobile computing device, and the like. In someembodiments, one or more member devices within member devices 102-104may be devices that are capable of connecting using a wired or wirelesscommunication medium such as a PDA, POCKET PC, wearable computer, alaptop, tablet, desktop computer, a netbook, a video game device, apager, a smart phone, an ultra-mobile personal computer (UMPC), and/orany other device that is equipped to communicate over a wired and/orwireless communication medium (e.g., NFC, RFID, NBIOT, 3G, 4G, 5G, GSM,GPRS, WiFi, WiMax, CDMA, satellite, ZigBee, etc.). In some embodiments,one or more member devices within member devices 102-104 may include mayrun one or more applications, such as Internet browsers, mobileapplications, voice calls, video games, videoconferencing, and email,among others. In some embodiments, one or more member devices withinmember devices 102-104 may be configured to receive and to send webpages, and the like. In some embodiments, an exemplary specificallyprogrammed browser application of the present disclosure may beconfigured to receive and display graphics, text, multimedia, and thelike, employing virtually any web based language, including, but notlimited to Standard Generalized Markup Language (SMGL), such asHyperText Markup Language (HTML), a wireless application protocol (WAP),a Handheld Device Markup Language (HDML), such as Wireless MarkupLanguage (WML), WMLScript, XML, JavaScript, and the like. In someembodiments, a member device within member devices 102-104 may bespecifically programmed by either Java, .Net, QT, C, C++ and/or othersuitable programming language. In some embodiments, one or more memberdevices within member devices 102-104 may be specifically programmedinclude or execute an application to perform a variety of possibletasks, such as, without limitation, messaging functionality, browsing,searching, playing, streaming or displaying various forms of content,including locally stored or uploaded messages, images and/or video,and/or games.

In some embodiments, the exemplary network 105 may provide networkaccess, data transport and/or other services to any computing devicecoupled to it. In some embodiments, the exemplary network 105 mayinclude and implement at least one specialized network architecture thatmay be based at least in part on one or more standards set by, forexample, without limitation, Global System for Mobile communication(GSM) Association, the Internet Engineering Task Force (IETF), and theWorldwide Interoperability for Microwave Access (WiMAX) forum. In someembodiments, the exemplary network 105 may implement one or more of aGSM architecture, a General Packet Radio Service (GPRS) architecture, aUniversal Mobile Telecommunications System (UMTS) architecture, and anevolution of UMTS referred to as Long Term Evolution (LTE). In someembodiments, the exemplary network 105 may include and implement, as analternative or in conjunction with one or more of the above, a WiMAXarchitecture defined by the WiMAX forum. In some embodiments and,optionally, in combination of any embodiment described above or below,the exemplary network 105 may also include, for instance, at least oneof a local area network (LAN), a wide area network (WAN), the Internet,a virtual LAN (VLAN), an enterprise LAN, a layer 3 virtual privatenetwork (VPN), an enterprise IP network, or any combination thereof. Insome embodiments and, optionally, in combination of any embodimentdescribed above or below, at least one computer network communicationover the exemplary network 105 may be transmitted based at least in parton one of more communication modes such as but not limited to: NFC,RFID, Narrow Band Internet of Things (NBIOT), ZigBee, 3G, 4G, 5G, GSM,GPRS, WiFi, WiMax, CDMA, satellite and any combination thereof. In someembodiments, the exemplary network 105 may also include mass storage,such as network attached storage (NAS), a storage area network (SAN), acontent delivery network (CDN) or other forms of computer or machinereadable media.

In some embodiments, the exemplary server 106 or the exemplary server107 may be a web server (or a series of servers) running a networkoperating system, examples of which may include but are not limited toMicrosoft Windows Server, Novell NetWare, or Linux. In some embodiments,the exemplary server 106 or the exemplary server 107 may be used forand/or provide cloud and/or network computing. Although not shown inFIG. 1, in some embodiments, the exemplary server 106 or the exemplaryserver 107 may have connections to external systems like email, SMSmessaging, text messaging, ad content providers, etc. Any of thefeatures of the exemplary server 106 may be also implemented in theexemplary server 107 and vice versa.

In some embodiments, one or more of the exemplary servers 106 and 107may be specifically programmed to perform, in non-limiting example, asauthentication servers, search servers, email servers, social networkingservices servers, SMS servers, IM servers, MMS servers, exchangeservers, photo-sharing services servers, advertisement providingservers, financial/banking-related services servers, travel servicesservers, or any similarly suitable service-base servers for users of themember computing devices 101-104.

In some embodiments and, optionally, in combination of any embodimentdescribed above or below, for example, one or more exemplary computingmember devices 102-104, the exemplary server 106, and/or the exemplaryserver 107 may include a specifically programmed software module thatmay be configured to send, process, and receive information using ascripting language, a remote procedure call, an email, a tweet, ShortMessage Service (SMS), Multimedia Message Service (MMS), instantmessaging (IM), internet relay chat (IRC), mIRC, Jabber, an applicationprogramming interface, Simple Object Access Protocol (SOAP) methods,Common Object Request Broker Architecture (CORBA), HTTP (HypertextTransfer Protocol), REST (Representational State Transfer), or anycombination thereof.

FIG. 2 depicts a block diagram of another exemplary computer-basedsystem/platform 200 in accordance with one or more embodiments of thepresent disclosure. However, not all of these components may be requiredto practice one or more embodiments, and variations in the arrangementand type of the components may be made without departing from the spiritor scope of various embodiments of the present disclosure. In someembodiments, the member computing devices 202 a, 202 b through 202 nshown each at least includes a computer-readable medium, such as arandom-access memory (RAM) 208 coupled to a processor 210 or FLASHmemory. In some embodiments, the processor 210 may executecomputer-executable program instructions stored in memory 208. In someembodiments, the processor 210 may include a microprocessor, an ASIC,and/or a state machine. In some embodiments, the processor 210 mayinclude, or may be in communication with, media, for examplecomputer-readable media, which stores instructions that, when executedby the processor 210, may cause the processor 210 to perform one or moresteps described herein. In some embodiments, examples ofcomputer-readable media may include, but are not limited to, anelectronic, optical, magnetic, or other storage or transmission devicecapable of providing a processor, such as the processor 210 of client202 a, with computer-readable instructions. In some embodiments, otherexamples of suitable media may include, but are not limited to, a floppydisk, CD-ROM, DVD, magnetic disk, memory chip, ROM, RAM, an ASIC, aconfigured processor, all optical media, all magnetic tape or othermagnetic media, or any other medium from which a computer processor canread instructions. Also, various other forms of computer-readable mediamay transmit or carry instructions to a computer, including a router,private or public network, or other transmission device or channel, bothwired and wireless. In some embodiments, the instructions may comprisecode from any computer-programming language, including, for example, C,C++, Visual Basic, Java, Python, Perl, JavaScript, and etc.

In some embodiments, member computing devices 202 a through 202 n mayalso comprise a number of external or internal devices such as a mouse,a CD-ROM, DVD, a physical or virtual keyboard, a display, or other inputor output devices. In some embodiments, examples of member computingdevices 202 a through 202 n (e.g., clients) may be any type ofprocessor-based platforms that are connected to a network 206 such as,without limitation, personal computers, digital assistants, personaldigital assistants, smart phones, pagers, digital tablets, laptopcomputers, Internet appliances, and other processor-based devices. Insome embodiments, member computing devices 202 a through 202 n may bespecifically programmed with one or more application programs inaccordance with one or more principles/methodologies detailed herein. Insome embodiments, member computing devices 202 a through 202 n mayoperate on any operating system capable of supporting a browser orbrowser-enabled application, such as Microsoft™ Windows™, and/or Linux.In some embodiments, member computing devices 202 a through 202 n shownmay include, for example, personal computers executing a browserapplication program such as Microsoft Corporation's Internet Explorer™,Apple Computer, Inc.'s Safari™, Mozilla Firefox, and/or Opera. In someembodiments, through the member computing client devices 202 a through202 n, users, 212 a through 212 n, may communicate over the exemplarynetwork 206 with each other and/or with other systems and/or devicescoupled to the network 206. As shown in FIG. 2, exemplary server devices204 and 213 may be also coupled to the network 206. In some embodiments,one or more member computing devices 202 a through 202 n may be mobileclients.

In some embodiments, at least one database of exemplary databases 207and 215 may be any type of database, including a database managed by adatabase management system (DBMS). In some embodiments, an exemplaryDBMS-managed database may be specifically programmed as an engine thatcontrols organization, storage, management, and/or retrieval of data inthe respective database. In some embodiments, the exemplary DBMS-manageddatabase may be specifically programmed to provide the ability to query,backup and replicate, enforce rules, provide security, compute, performchange and access logging, and/or automate optimization. In someembodiments, the exemplary DBMS-managed database may be chosen fromOracle database, IBM DB2, Adaptive Server Enterprise, FileMaker,Microsoft Access, Microsoft SQL Server, MySQL, PostgreSQL, and a NoSQLimplementation. In some embodiments, the exemplary DBMS-managed databasemay be specifically programmed to define each respective schema of eachdatabase in the exemplary DBMS, according to a particular database modelof the present disclosure which may include a hierarchical model,network model, relational model, object model, or some other suitableorganization that may result in one or more applicable data structuresthat may include fields, records, files, and/or objects. In someembodiments, the exemplary DBMS-managed database may be specificallyprogrammed to include metadata about the data that is stored.

As also shown in FIGS. 2 and 3, some embodiments of the disclosedtechnology may also include and/or involve one or more cloud components225, which are shown grouped together in the drawing for sake ofillustration, though may be distributed in various ways as known in theart. Cloud components 225 may include one or more cloud services such assoftware applications (e.g., queue, etc.), one or more cloud platforms(e.g., a Web front-end, etc.), cloud infrastructure (e.g., virtualmachines, etc.), and/or cloud storage (e.g., cloud databases, etc.).

According to some embodiments shown by way of one example in FIG. 4, theexemplary inventive computer-based systems/platforms, the exemplaryinventive computer-based devices, components and media, and/or theexemplary inventive computer-implemented methods of the presentdisclosure may be specifically configured to operate in or with cloudcomputing/architecture such as, but not limiting to: infrastructure aservice (IaaS) 410, platform as a service (PaaS) 408, and/or software asa service (SaaS) 406. FIGS. 3 and 4 illustrate schematics of exemplaryimplementations of the cloud computing/architecture(s) in which theexemplary inventive computer-based systems/platforms, the exemplaryinventive computer-implemented methods, and/or the exemplary inventivecomputer-based devices, components and/or media of the presentdisclosure may be specifically configured to operate.

In various embodiments, different aspects described with respect toFIGS. 1-4 may be used. For example, client devices 102, 103, and 104 ofFIG. 1 may share information updates with one another via the network105 without the information updates being processed or routed throughthe network servers 106, 107. Similarly, client devices 202 a through202 n FIG. 2 may share information updates with one another via thenetwork 206 without routing the information update through the serverdevices 204 and 213, and/or without routing the information updatethrough the cloud components 225. In other words, the client devicesshown in FIGS. 1 and 2 may transmit push-based information updates toone another without routing such information updates through a server.In the examples of FIGS. 1 and 2, the information updates may be routedthrough network infrastructure and devices. However, in other variousembodiments described herein, information updates may be routed throughno intermediate network infrastructure. In various embodiments, thenetwork infrastructure may also include various types of networks orvarious network components. For example, FIGS. 7-10 show furtherexamples of network infrastructure that may be used to route informationupdates. In various embodiments, various combinations of the componentsshown in FIGS. 1-4 and 7-10 may be used to implement the systems andmethods described herein.

In various embodiments, information updates may be routed to a server orcloud components, such that endpoint devices for an information updatemay include a server or cloud component. In other words, an informationupdate may be pushed to server or cloud devices as well as otheruser/client devices. However, in such embodiments, the information isnot routed through a server or cloud component to other client devices.Rather, the server or cloud components are merely another device towhich information updates may be pushed. This may be useful where, forexample, a user backs up the data from their client device on a remoteserver. In this way, even though the information updates may be routedto server or cloud component, all the advantages as described herein maystill be accomplished.

FIG. 5 is a flowchart illustrating a process 500 for push-basedtransmissions using the target as a system of record in accordance withone or more embodiments of the present disclosure. The process 500includes operations that may be performed, for example, by a clientdevice of FIGS. 1, 2, and/or 7-10.

At an operation 502, user profile configuration information thatidentifies a user is received by a computing device, such as a clientdevice of FIGS. 1, 2, and/or 7-10. User profile configurationinformation may include any information that identifies a user, such asdemographic data, name, address, government issued identification orsocial security number, age, birth date, place of birth, login name,password, biometric information (e.g., fingerprint, face), etc. A usermay enter such information to identify themselves, so that their use ofthe device may be correlated to the user identified by the user profileconfiguration information. Accordingly, with the user profileconfiguration information, a device may be associated with a particularuser, and subsequently with other users and/or devices to whichinformation updates are sent.

At an operation 504, a recipient list for push-based information updatesis determined. In other words, the system may determine a recipient listthat includes identifying devices to which information updates should besent. Such information may be determined in various ways. For example,the recipients for an information update may be devices associated withother users that a user of the client device has previously indicatedinformation updates should be sent to. In other words, a user may selectwhich other devices/users information updates may be sent to. Recipientsmay also be users/devices to which an update has previously been sentmanually. In addition, a user may indicate which types of informationchanges should be sent out to other devices. In such examples, therecipient list determined may therefore be different for different typesof information changes detected. For example, information of a certaintype and/or information associated with a particular application may beassociated with different recipients. Any combination of methods fordetermining a recipient list may also be used. For example, a recipientlist may be determined based on a type of information, who previousrecipients of that type of information update are, and/or anyrecipients/users that have been manually specified for distribution. Insome embodiments, a recipient device may transmit a request to subscribeto certain types of information updates and/or for a specific type ofinformation. If a user approves sharing information and/or informationupdates with the requester, that requester device may be considered tobe part of a recipient list for that type of data should a change orupdate be detected for that data in the future.

A recipient list may also be associated the user profile configurationinformation. In other words, the devices determined to be on a recipientlist may be linked or otherwise determined based on information in theuser profile configuration information. For example, updates may beshared with other devices upon which a user has logged into with thesame user profile configuration information because, for example, thosedevices are presumably owned by or controlled by the same person, user,family, etc. The user profile configuration information may further beused to determine recipients for the information updates that are notthe user themselves. For example, the user profile configurationinformation may be used to determine known contacts to which informationupdates should be sent, such as recipient devices previously determinedto be recipient devices on a different device which has already receivedthe sender's user profile configuration information.

In various embodiments, a user may also be able to deselect or opt outof sending certain devices/users information updates. For example, aninformation update of a certain type may have been sent to a particulardevice/user before, but a user interface of the sender device may beused to deselect that particular device/user so that it is no longer arecipient device. That deselection may be made to deselect a clientdevice for all information updates, or may be deselected for onlycertain information types.

A sender device may also receive a message from a recipient device thatincludes a request to opt out of future information updates. Such arequest may be related to all information updates from the senderdevice, or just one or more specific types of information updates. Thesender device may use such requests to further determine a recipientlist. That is, when a recipient requests to not be sent informationupdates, the sender device does not include that recipient whendetermining a recipient list for an information update.

At an operation 506, an information set or application for thepush-based information updates is determined. This operation may beperformed in concert with the operation 504 if an information update isto be transmitted to recipients based on the type of information orapplication the information update is related to. However, in any case,the operation includes determining which information sets orapplications should actually be monitored for push-based informationupdates. Such information sets or applications may be default set on adevice, may be manually defined by a user, may be set over time as theuser agrees to have certain information sets or applications share dataor otherwise be monitored for changes, etc. For example, a user mayreceive a request to send contact information with a different userdevice. After such a transmission occurs, the device may determine thatthe information set on the device including the sending user's contactinformation should be monitored for changes if it was not already, sothat in the future if the sender's device updates its contactinformation such updates can be pushed to other devices. In variousembodiments the user's device may also prompt the user for permission tomonitor a particular information set or application for updates beforemonitoring that information set or application.

At an operation 508, an input including a change to the information setor the application is received at the client device. For example, theuser may manually change the information, may use an application tochange information associated with an application, etc. In some cases,the information may not be manually updated by the user. For example,the information may be automatically updated by the device afterreceiving the information from a different device. In variousembodiments, the updates may be received or input to the device in anymanner.

At an operation 510, a daemon process runs as a background process of anoperating system of the computing device to monitor the information setor application for changes. The daemon process may run in the backgroundas part of the operating system of the device so that a particularapplication need not run to determine when changes to an information setoccur. Accordingly, the daemon process monitoring for changes may beoperating whenever the client device is operating.

At an operation 512, upon receiving the change to the information set orthe application at the operation 508, the daemon process automaticallytransmits the change to the information set or the application directlyto the plurality of other computing devices determined to part of therecipient list for the push-based information updates at the operation504. By sending the information updates directly to the other devices,the information updates may be received by the recipient devices withoutbeing received by any intermediate devices. In other words, thedetermining of the recipients at the originator or sender device removesany need for intermediate receipt, processing, and transmitting of theinformation update at another device, such as a server. While networkinfrastructure devices or other devices may be used to route theinformation update to the recipient devices, those devices used to routethe push-based update would not read the actual information update orprocess it, the routing devices would merely help route the update tothe proper recipient devices. In other words, the information may bepushed through intermediate communications infrastructure devices. Insome embodiments, however, the information may be pushed directlybetween devices without being transmitted to or retransmitted by anyintermediate communications devices (e.g., if the sender and recipientdevice are configured to communicate directly with one another).

In some embodiments, the push-based updates may be transmitted throughinternet and/or non-internet connected communications infrastructuredevices. For example, such push-based updates may be transmitted througha satellite communications network, a peer to peer communicationsnetwork, or any other network and its associated devices as acommunications relay. Even if some of the devices are connected to theinternet (e.g., sender device, recipient device, intermediatecommunications infrastructure device), the push-based informationupdates may not be sent over the internet or using internetinfrastructure.

In any case, the daemon process is therefore configured to monitor theinformation set or the application for the change and automaticallytransmit the change directly to the plurality of other computing devicesso as to push the change upon the receiving of the change to theinformation set or the application. Such a method further removes anyneed for the user to be involved in pushing a particular, individualupdate to the recipient devices. In addition, the methods and systemsdescribed herein provide for pushing changes to an information set orapplication without necessitating a handshake process between the senderand recipient device. In many communications, devices establish aconnection with one another via a series of transmit and receiptmessages. However, in various embodiments, the sender device may justtransmit information updates without determining whether thecommunication with the recipient device(s) has been established, andwithout the need to receive a confirmation receipt that the transmissionwas received.

The information set that may be monitored for updates may be any type ofinformation on a client device. For example, the information set may berelated to or may be a document, a word processing application ordocument, contact information, demographic information, mailing address,financial account information, information associated with the client orcomputing device, or information of another computing or client deviceassociated with a user. Information sets that are part of an applicationor stored on the client device by an application may also be monitoredfor changes. In other words, any type of information stored on a clientdevice may be monitored for changes.

FIG. 6 is a flowchart illustrating another process 600 for push-basedtransmissions using the target as a system of record in accordance withone or more embodiments of the present disclosure. The process 500includes operations that may be performed, for example, by a clientdevice of FIGS. 1, 2, and/or 7-10.

At an operation 602, the user profile configuration informationidentifying a user is received by the client device. The operation 602may be similar to the operation 502 of the process 500 described above.The user profile configuration information may further includeinformation for identifying a user financial account (e.g., brokerageaccount, savings account, checking account, money market account, etc.).In this way, the client device may be used in connection with actionsrelated to the user's financial account(s).

At an operation 604, a recipient computing device for push-basedinformation updates is determined based on the user profileconfiguration information. For example, the recipient computing devicemay be associated with a financial institution with which the user hasan account (e.g., by way of financial account information entered aspart of the user profile configuration information). The recipientcomputing device for push-based information updates may therefore be oneor more computing devices associated with the financial institution. Inthis way, the sender computing device may send information updatesautomatically to the user's financial institution.

At an operation 606, transaction details of a transaction that hasoccurred related to the user's financial account are determined. Forexample, a user may use their phone to pay for something using Zelle™,or any other type of payment processing, including payment processingthat uses near field contact (NFC) devices or a scannable visual code toscan the phone to pay for something. Typically, a payment processingdevice and/or point of sale (POS) device may be used to scan an NFC orvisual code for payment, and the payment processing device and/or POSdevice will process the payment, approve the payment, etc. The financialinstitution typically relies on that information from the paymentprocessor and/or the retailer's POS device for the transaction details.The user is then responsible for checking their financial account tomake sure that charges to their account are correct. In the embodimentsdescribed herein, the user's client device may also scan somethingrelated to the transaction (e.g., if using an NFC device the clientdevice and payment processing device may communicate the transactiondetails, if using scannable visual codes the client device may scan acode indicating the transaction details). In any case, since thetransaction details are determined by the client device, the transactiondetails may be an information change pushed to the financial institutiondevice as further described below.

In an operation 608 a daemon process runs as a background process of anoperating system of the client device so that changes in informationsets (e.g., including for new transactions that have occurred using theclient device) may be detected and pushed according the variousembodiments described herein. The operation 608 may be similar to theoperation 510 of the process 500 described above.

At an operation 610, upon determining that a transaction has occurredusing the daemon process of the operating system, the daemon processalso automatically transmits/pushes the transaction details to therecipient computing device associated with the financial institution. Inother words, the daemon process is configured to monitor the computingdevice for transactions that occur and automatically transmit thetransaction details directly to the recipient computing deviceassociated by the financial institution without being received by anyintermediate devices so as to push the transaction details upon thedetermining that the transaction has occurred. The transaction detailscomprise information configured for verification of the transaction bythe financial institution. In other words, the transaction details maybe used by the financial institution to verify the transaction detailsreceived from the retailer, the payment processor, the POS device, thepayment processing device, etc. This advantageously offers an additionallayer of security to prevent fraudulent transactions for both the clientand the financial institution. By receiving the transaction details fromthe known client device and the retailer or payment processor, thefinancial institution can make sure the transaction details receivedfrom the client device matches the other transaction details. Inaddition, since the transaction details may be sent directly to thefinancial institution device without intermediate processing, suchverification may take place quickly and easily.

The transaction details may include at least one of a transactionamount, a payment method, a merchant name, a timestamp, whether apurchase was in-store or online, geographic location information of thecomputing device at a time of the transaction, or any other informationthat may be useful in verifying a transaction. For example, thegeographic location may be useful to determine that the client devicewas actually at the retailer location where the payment was made for anin-store purchase.

Information for providing payment for the transaction may be provided toa payment processing device from the client device as described herein(e.g., through NFC, scannable visual codes, etc.). The details of thetransaction may further include identifying information associated withthe client device, as needed to authorize a payment for the transaction.For an in-store payment, the payment processing device may be physicallyproximate to the client device when the information for providingpayment for the transaction is transmitted to the payment processingdevice (e.g., in the NFC context). The recipient computing device may bephysically remote from both the payment processing device and the clientdevice at the time of the transaction. In other words, the client andpayment processing device may be present where the transaction is takingplace, but the financial institution device that receives the push-basedinformation update may be remote to both devices. The transactiondetails from the client device may then be compared to information aboutthe transaction provided by a payment processor or merchant for fraudprevention.

FIGS. 7-10 show further example systems that may be used according tothe embodiments described herein. In particular, they demonstratedifferent types of network infrastructure that may be used to routeinformation-based updates to various client devices. As describedherein, such infrastructure devices may be used merely to routepush-based information updates, and do not themselves process theinformation updates, determine recipients for the information updates,etc. Instead, such intermediate infrastructure devices may merely serverto follow instructions received from the original sender client deviceto route a message to a recipient device, agnostic of the content of themessage and/or the information updates or types of information updatedtherein. The devices, components, etc. of FIGS. 1-4 and 7-10 may be usedin any configuration or in combination with one another in variousembodiments. In other words, different embodiments may be used that usevarious configurations of client device types, communicationinfrastructure devices of different types, etc.

FIG. 7 is a block diagram of a system 700 with base stations forpush-based transmissions using the target as a system of record inaccordance with one or more embodiments of the present disclosure. Inparticular, the system 700 includes client devices 702 and 714. Theclient devices 702 and 714 may be, for example, smartphones. The clientdevices 702 and 714 may be configured to communicate with base stations704 and 712, respectively, of a cellular phone and data network, forexample. The base stations 704 and 712 may be, for example, located oncell towers, buildings, or other structures for providing cellular basedphone and data services through a voice/text/data switching networkinfrastructure 706.

The voice/text/data switching network infrastructure 706 may also bepart of the cellular network and facilitate communication between thebase stations 704 and 712, and subsequently the client devices 702 and714. The voice/text/data switching network infrastructure 706 may alsofacilitate communication with devices outside of the cellular network,such as landline phone numbers through a public switched telephonenetwork (PSTN) 710 and/or other devices capable of processing data suchas the server 708. In some embodiments, the voice/text/data switchingnetwork infrastructure 706 may communicate with the server 708 over theinternet, and the voice/text/data switching network infrastructure 706may enable communication with any other devices over the internet. Assuch, the client device 702, for example, may push information updatesto recipient devices such as the client device 714 and/or the server 708as described herein using the network infrastructure devices (e.g., thebase stations 704 and 712, the voice/text/data switching networkinfrastructure 706) of FIG. 7.

FIG. 8 is a block diagram of a system 800 with wireless access points(WAP) for push-based transmissions using the target as a system ofrecord in accordance with one or more embodiments of the presentdisclosure. The system 800 includes client devices 802, 806, 814, and820. The system 800 further includes wireless access points (WAP) 804,812, and 816. WAPs 804, 812, and 816 may be, for example, wirelessrouters (e.g., WiFi) for connecting to internet network infrastructure808. IN this way, the client devices 802, 806, 814, and/or 820 may pushinformation updates to one another and/or receive information updatesfrom one another as described herein without intermediate processing byanother device (e.g., a server 810). However, in some embodiments, theserver 810 may be a recipient for information updates and/or mayoriginate information updates to be pushed to other devices.

In various embodiments, the information updates may be routed and ortransmitted between devices in different ways. For example, aninformation update from the client device 802 to the client device 820may be routed through the WAP 804, the internet network infrastructure808, and the WAP 816 to reach the client device 820 because the clientdevice 802 and the client device 820 are not within range to communicatewith one another directly. In another embodiment, a connection to theinternet network infrastructure 808 of the WAP 812 may be out orotherwise nonexistent as indicated by the broken line connector 822.However, in some embodiments, the WAP 812 may still be in connectionwith the WAP 804 (whether or not the WAP 804 is connected to theinternet infrastructure). Accordingly, an information update may bepushed from the client device 806 to the WAP 804, to the WAP 812, andthen to the client device 814. Such an information update may be pushedeven in the event that neither of WAP 804 and 812 are connected to theinternet network infrastructure 808. That is, network infrastructuredevices such as the WAPs 804, 812, 816 etc. may be used to facilitatepush-based information updates even in the absence of connections to thewider internet (e.g., a closed network may be used).

FIG. 9 is a block diagram of a system 900 with satellites for push-basedtransmissions using the target as a system of record in accordance withone or more embodiments of the present disclosure. The system 900includes client devices 902, 910, and 914 as well as satellites 904 and912. The system 900 further includes a server 908 and satellitecommunication infrastructure 906. The satellites 904 and 912 may includenetwork infrastructure communication devices on an orbiting satellitethat is capable of communication with the client devices 902, 910, and914. Only certain satellites may be within range of a client device atany given time. For example, the client devices 902 and 910 are withincommunication range of the satellite 904 while the client device 914 isin range with the satellite 912.

The satellites 904 and 912 may therefore be used as networkinfrastructure devices to facilitate push-based information updates asdescribed herein, with or without connections to a wider network such asthe internet. For example, the client device 902 may push an update tothe client device 910, which may only be routed through the satellite904. The client device 910 may push an update to the client device 914,which may be routed through the satellites 904 and 912, or through eachof the satellites 904, 912 and the satellite communicationinfrastructure. The satellite communication infrastructure may be groundbased infrastructure allowing the satellites 904 and 912 to communicatewith each other or with other satellites if direct communication betweensatellites is not possible. The satellite communication infrastructure906 may facilitate communication with other devices, such as the server908, which may be a recipient of or originator of push-based informationupdates as well. The satellite communication infrastructure 906 mayfacilitate communications with other networks and devices connectedthereto, such as the internet.

FIG. 10 is a block diagram of a system 1000 with a mesh network ofclient devices for push-based transmissions using the target as a systemof record in accordance with one or more embodiments of the presentdisclosure. A mesh network may be a peer to peer network of clientdevices for transmitting push-based information updates. In a givengroup of client devices 1002, 1004, 1006, 1008, and 1010, the devicesmay be outside of range of direct communication with one another (e.g.,through Bluetooth or other communication protocols). For example, theclient device 1004 is only in range to communicate with the clientdevices 1002, 1006, and 1008. However, the client device 1004 may stillroute a push-based update to or receive a push-based update from theclient device 1010 through the client devices 1008 and/or 1006. In thisway, a large number of client devices may form a network of clientdevices that may route updates to one another without the use of aseparate network or network infrastructure.

In the example of FIG. 10, for a given information update being pushed,some client devices may act as network infrastructure. In other words,if the client device 1006 pushes an update to the client device 1002 viathe client device 1004, the client device 1004 may act as networkinfrastructure, and may not process or read the information basedupdate, but rather may just route the push-based update onto the clientdevice 1002.

This mesh network may also change as the client devices move and comeinto and out communication range with one another. For example, theclient device 1002 may move into range of direct communication with theclient device 1010. In such an example, information updates may be sentto the client device 1010 directly rather than be routed through theclient devices 1004, 1006, and/or 1008.

In some embodiments of the system of FIG. 10, the push-based updates maybe broadcast from the sender device, such that any client device inrange may receive the push-based update and instructions for routing thepush-based update to the correct client device. A client devicereceiving such a broadcast may in turn broadcast the update if it is notthe intended recipient of the push-based update. In this way, the updatemay eventually reach the intended device even if the client devices donot have awareness of which other client devices they are in contactwith (e.g., they do not know how the network connections are currentlyconfigured).

At least some aspects of the present disclosure will now be describedwith reference to the following numbered clauses.

-   1. A method comprising:    -   receiving, by a processor of a computing device, user profile        configuration information identifying a user;    -   determining, by the processor, a recipient list for push-based        information updates, wherein the recipient list comprises a        plurality of other computing devices and the recipient list is        associated with the user profile configuration information;    -   determining, by the processor, an information set or application        for the push-based information updates;    -   receiving, by the processor, an input comprising a change to the        information set or the application; and    -   running, by the processor, a daemon process as a background        process of an operating system of the computing device,    -   wherein the daemon process is configured to monitor the        information set or the application for the change and        automatically transmit the change directly to the plurality of        other computing devices without being received by any        intermediate devices so as to push the change upon the receiving        of the input comprising the change to the information set or the        application.-   2. The method of clause 1, wherein the determining of the recipient    list comprises determining the computing devices with which the    computing device has previously shared the information set or data    associated with the application.-   3. The method of clause 2, wherein the determining of the recipient    list further comprises determining computing devices with which the    user of the computing device has opted into sharing the information    set or data associated with the application.-   4. The method of clause 1, further comprising receiving, by the    processor, a deselection of one of the plurality of other computing    devices of the recipient list, such that a deselected one of the    plurality of other computing devices is removed from the recipient    list.-   5. The method of clause 1, wherein the information set or the    application comprises at least one of a specific document, a word    processing application, contact information, demographic    information, mailing address, financial account information,    information associated with the computing device, or information of    another computing device associated with the user.-   6. The method of clause 1, the determining of the recipient list and    the information set or the application for the push-based    information updates comprises:    -   receiving, by the processor, a first user input indicating a        first plurality of other computing devices to which changes to a        first information set or a first application are transmitted;        and    -   receiving, by the processor, a second user input indicating a        second plurality of other computing devices to which changes to        a second information set or a second application are        transmitted.-   7. The method of clause 1, wherein the automatic transmit of the    change comprises transmitting the change directly to the plurality    of other computing devices without being transmitted through any    intermediate communications infrastructure.-   8. The method of clause 1, wherein the computing device is a first    computing device associated with the user, and further wherein at    least a second computing device is also associated with the user.-   9. The method of clause 8, wherein the change to the information set    or the application is also transmitted to the second computing    device.-   10. A system comprising:    -   a memory;    -   a display; and    -   at least one processor of a computing device that is coupled to        the memory, the at least one processor configured to:        -   receive user profile configuration information identifying a            user;        -   determine a recipient list for push-based information            updates, wherein the recipient list comprises a plurality of            other computing devices and the recipient list is associated            with the user profile configuration information;        -   determine an information set or application for the            push-based information updates;        -   receive an input comprising a change to the information set            or the application; and        -   run a daemon process as a background process of an operating            system of the computing device,        -   wherein the daemon process is configured to monitor the            information set or the application for changes and            automatically transmit the change to the information set or            the application upon the receiving of the input comprising            the change to the information set or the application.-   11. The system of clause 10, wherein the automatic transmit of the    change comprises transmitting the change to the plurality of other    computing devices via a non-internet connected communications    infrastructure.-   12. The system of clause 10, wherein the automatic transmit of the    change comprises transmitting the change to the plurality of other    computing devices via a satellite as a communications relay.-   13. The system of clause 10, wherein the automatic transmit of the    change is configured to be transmitted over internet infrastructure,    but is never received at or re-transmitted by an intermediate server    associated with the information set or the application.-   14. The system of clause 13, wherein the change to the information    set or the application is transmitted to the plurality of other    computing devices without a handshake process occurring between the    computing device and any of the plurality of other computing    devices.-   15. The system of clause 13, further comprising:    -   receiving, by the at least one processor, a request to be        removed from the recipient list from one of the plurality of        other computing devices of the recipient list comprising; and    -   removing, by the at least one processor, the one of the        plurality of other computing devices from the recipient list.-   16. A non-transitory computer readable medium having instructions    stored thereon that, upon execution by a computing device, cause the    computing device to perform operations comprising:    -   receiving user profile configuration information identifying a        user;    -   determining a recipient computing device for push-based        information updates based on the user profile configuration        information, wherein the recipient computing device is        associated with a financial institution with which the user has        an account;    -   determining transaction details of a transaction that has        occurred related to the account; and    -   running a daemon process as a background process of an operating        system of the computing device,    -   wherein the daemon process is configured to monitor the        computing device for transactions that occur and automatically        transmit the transaction details directly to the recipient        computing device without being received by any intermediate        devices so as to push the transaction details upon the        determining that the transaction has occurred, and    -   wherein the transaction details comprise information configured        for verification of the transaction by the financial        institution.-   17. The non-transitory computer readable medium of clause 16,    wherein the transaction details comprise at least one of a    transaction amount, a payment method, a merchant name, a timestamp,    whether a purchase was in-store or online, or geographic location    information of the computing device at a time of the transaction.-   18. The non-transitory computer readable medium of clause 16,    wherein the instructions further cause the computing device to    perform operations comprising transmitting, to a payment processing    device, information for providing payment for the transaction, and    wherein the transaction details comprise identifying information    associated with the computing device.-   19. The non-transitory computer readable medium of clause 18,    wherein the payment processing device is physically proximate to the    computing device when the information for providing payment for the    transaction is transmitted to the payment processing device, and    further wherein the recipient computing device is physically remote    from both the payment processing device and the computing device at    a time of the transaction.-   20. The non-transitory computer readable medium of clause 16,    wherein the transaction details are configured to be compared to    information about the transaction provided by a payment processor or    merchant for fraud prevention.

As used herein, the terms “computer engine” and “engine” identify atleast one software component and/or a combination of at least onesoftware component and at least one hardware component which aredesigned/programmed/configured to manage/control other software and/orhardware components (such as the libraries, software development kits(SDKs), objects, etc.).

Examples of hardware elements may include processors, microprocessors,circuits, circuit elements (e.g., transistors, resistors, capacitors,inductors, and so forth), integrated circuits, application specificintegrated circuits (ASIC), programmable logic devices (PLD), digitalsignal processors (DSP), field programmable gate array (FPGA), logicgates, registers, semiconductor device, chips, microchips, chip sets,and so forth. In some embodiments, the one or more processors may beimplemented as a Complex Instruction Set Computer (CISC) or ReducedInstruction Set Computer (RISC) processors; x86 instruction setcompatible processors, multi-core, or any other microprocessor orcentral processing unit (CPU). In various implementations, the one ormore processors may be dual-core processor(s), dual-core mobileprocessor(s), and so forth.

Examples of software may include software components, programs,applications, computer programs, application programs, system programs,machine programs, operating system software, middleware, firmware,software modules, routines, subroutines, functions, methods, procedures,software interfaces, application program interfaces (API), instructionsets, computing code, computer code, code segments, computer codesegments, words, values, symbols, or any combination thereof.Determining whether an embodiment is implemented using hardware elementsand/or software elements may vary in accordance with any number offactors, such as desired computational rate, power levels, heattolerances, processing cycle budget, input data rates, output datarates, memory resources, data bus speeds and other design or performanceconstraints.

One or more aspects of at least one embodiment may be implemented byrepresentative instructions stored on a machine-readable medium whichrepresents various logic within the processor, which when read by amachine causes the machine to fabricate logic to perform the techniquesdescribed herein. Such representations, known as “IP cores” may bestored on a tangible, machine readable medium and supplied to variouscustomers or manufacturing facilities to load into the fabricationmachines that make the logic or processor. Of note, various embodimentsdescribed herein may, of course, be implemented using any appropriatehardware and/or computing software languages (e.g., C++, Objective-C,Swift, Java, JavaScript, Python, Perl, QT, etc.).

In some embodiments, one or more of exemplary inventive computer-basedsystems/platforms, exemplary inventive computer-based devices, and/orexemplary inventive computer-based components of the present disclosuremay include or be incorporated, partially or entirely into at least onepersonal computer (PC), laptop computer, ultra-laptop computer, tablet,touch pad, portable computer, handheld computer, palmtop computer,personal digital assistant (PDA), cellular telephone, combinationcellular telephone/PDA, television, smart device (e.g., smart phone,smart tablet or smart television), mobile internet device (MID),messaging device, data communication device, and so forth.

As used herein, the term “server” should be understood to refer to aservice point which provides processing, database, and communicationfacilities. By way of example, and not limitation, the term “server” canrefer to a single, physical processor with associated communications anddata storage and database facilities, or it can refer to a networked orclustered complex of processors and associated network and storagedevices, as well as operating software and one or more database systemsand application software that support the services provided by theserver. Cloud components (e.g., FIGS. 3 and 4) and cloud servers areexamples.

In some embodiments, as detailed herein, one or more of thecomputer-based systems of the present disclosure may obtain, manipulate,transfer, store, transform, generate, and/or output any digital objectand/or data unit (e.g., from inside and/or outside of a particularapplication) that can be in any suitable form such as, withoutlimitation, a file, a contact, a task, an email, a message, a map, anentire application (e.g., a calculator), data points, and other suitabledata. In some embodiments, as detailed herein, one or more of thecomputer-based systems of the present disclosure may be implementedacross one or more of various computer platforms such as, but notlimited to: (1) Linux™, (2) Microsoft Windows™, (3) OS X (Mac OS), (4)Solaris™, (5) UNIX™ (6) VMWare™, (7) Android™, (8) Java Platforms™, (9)Open Web Platform, (10) Kubernetes or other suitable computer platforms.In some embodiments, illustrative computer-based systems or platforms ofthe present disclosure may be configured to utilize hardwired circuitrythat may be used in place of or in combination with softwareinstructions to implement features consistent with principles of thedisclosure. Thus, implementations consistent with principles of thedisclosure are not limited to any specific combination of hardwarecircuitry and software. For example, various embodiments may be embodiedin many different ways as a software component such as, withoutlimitation, a stand-alone software package, a combination of softwarepackages, or it may be a software package incorporated as a “tool” in alarger software product.

For example, exemplary software specifically programmed in accordancewith one or more principles of the present disclosure may bedownloadable from a network, for example, a website, as a stand-aloneproduct or as an add-in package for installation in an existing softwareapplication. For example, exemplary software specifically programmed inaccordance with one or more principles of the present disclosure mayalso be available as a client-server software application, or as aweb-enabled software application. For example, exemplary softwarespecifically programmed in accordance with one or more principles of thepresent disclosure may also be embodied as a software package installedon a hardware device.

In some embodiments, illustrative computer-based systems or platforms ofthe present disclosure may be configured to handle numerous concurrentusers that may be, but is not limited to, at least 100 (e.g., but notlimited to, 100-999), at least 1,000 (e.g., but not limited to,1,000-9,999), at least 10,000 (e.g., but not limited to, 10,000-99,999),at least 100,000 (e.g., but not limited to, 100,000-999,999), at least1,000,000 (e.g., but not limited to, 1,000,000-9,999,999), at least10,000,000 (e.g., but not limited to, 10,000,000-99,999,999), at least100,000,000 (e.g., but not limited to, 100,000,000-999,999,999), atleast 1,000,000,000 (e.g., but not limited to,1,000,000,000-999,999,999,999), and so on.

In some embodiments, exemplary inventive computer-basedsystems/platforms, exemplary inventive computer-based devices, and/orexemplary inventive computer-based components of the present disclosuremay be configured to output to distinct, specifically programmedgraphical user interface implementations of the present disclosure(e.g., a desktop, a web app., etc.). In various implementations of thepresent disclosure, a final output may be displayed on a displayingscreen which may be, without limitation, a screen of a computer, ascreen of a mobile device, or the like. In various implementations, thedisplay may be a holographic display. In various implementations, thedisplay may be a transparent surface that may receive a visualprojection. Such projections may convey various forms of information,images, and/or objects. For example, such projections may be a visualoverlay for a mobile augmented reality (MAR) application.

In some embodiments, exemplary inventive computer-basedsystems/platforms, exemplary inventive computer-based devices, and/orexemplary inventive computer-based components of the present disclosuremay be configured to be utilized in various applications which mayinclude, but not limited to, gaming, mobile-device games, video chats,video conferences, live video streaming, video streaming and/oraugmented reality applications, mobile-device messenger applications,and others similarly suitable computer-device applications.

As used herein, the term “mobile electronic device,” or the like, mayrefer to any portable electronic device that may or may not be enabledwith location tracking functionality (e.g., MAC address, InternetProtocol (IP) address, or the like). For example, a mobile electronicdevice can include, but is not limited to, a mobile phone, PersonalDigital Assistant (PDA), Blackberry™, Pager, Smartphone, or any otherreasonable mobile electronic device.

As used herein, the terms “proximity detection,” “locating,” “locationdata,” “location information,” and “location tracking” refer to any formof location tracking technology or locating method that can be used toprovide a location of, for example, a particular computingdevice/system/platform of the present disclosure and/or any associatedcomputing devices, based at least in part on one or more of thefollowing techniques/devices, without limitation: accelerometer(s),gyroscope(s), Global Positioning Systems (GPS); GPS accessed usingBluetooth™; GPS accessed using any reasonable form of wireless and/ornon-wireless communication; WiFi™ server location data; Bluetooth™ basedlocation data; triangulation such as, but not limited to, network basedtriangulation, WiFi™ server information based triangulation, Bluetooth™server information based triangulation; Cell Identification basedtriangulation, Enhanced Cell Identification based triangulation,Uplink-Time difference of arrival (U-TDOA) based triangulation, Time ofarrival (TOA) based triangulation, Angle of arrival (AOA) basedtriangulation; techniques and systems using a geographic coordinatesystem such as, but not limited to, longitudinal and latitudinal based,geodesic height based, Cartesian coordinates based; Radio FrequencyIdentification such as, but not limited to, Long range RFID, Short rangeRFID; using any form of RFID tag such as, but not limited to active RFIDtags, passive RFID tags, battery assisted passive RFID tags; or anyother reasonable way to determine location. For ease, at times the abovevariations are not listed or are only partially listed; this is in noway meant to be a limitation.

In some embodiments, the exemplary inventive computer-basedsystems/platforms, the exemplary inventive computer-based devices,and/or the exemplary inventive computer-based components of the presentdisclosure may be configured to securely store and/or transmit data byutilizing one or more of encryption techniques (e.g., private/public keypair, Triple Data Encryption Standard (3DES), block cipher algorithms(e.g., IDEA, RC2, RCS, CAST and Skipjack), cryptographic hash algorithms(e.g., MD5, RIPEMD-160, RTRO, SHA-1, SHA-2, Tiger (TTH), WHIRLPOOL,RNGs).

Publications cited throughout this document are hereby incorporated byreference in their entirety. While one or more embodiments of thepresent disclosure have been described, it is understood that theseembodiments are illustrative only, and not restrictive, and that manymodifications may become apparent to those of ordinary skill in the art,including that various embodiments of the inventive methodologies, theinventive systems/platforms, and the inventive devices described hereincan be utilized in any combination with each other. Further still, thevarious steps may be carried out in any desired order (and any desiredsteps may be added and/or any desired steps may be eliminated).

What is claimed is:
 1. A method comprising: receiving, by a processor ofa computing device, user profile configuration information identifying afirst user; determining, by the processor, a recipient list forpush-based information updates, wherein the recipient list comprises aplurality of other computing devices that are each associated with aplurality of users other than the first user, and the recipient list isassociated with the user profile configuration information; determining,by the processor, an information set or application for the push-basedinformation updates; receiving, by the processor, an input comprising achange to the information set or the application; and running, by theprocessor, a daemon process as a background process of an operatingsystem of the computing device, wherein the daemon process is configuredto monitor the information set or the application for the change andautomatically transmit the change directly to the plurality of othercomputing devices without being received by any intermediate devices soas to push the change upon the receiving of the input comprising thechange to the information set or the application, wherein the change istransmitted to the plurality of other computing devices withoutreceiving a request for the change from any of the plurality ofcomputing devices.
 2. The method of claim 1, wherein the determining ofthe recipient list comprises determining the computing devices withwhich the computing device has previously shared the information set ordata associated with the application.
 3. The method of claim 2, whereinthe determining of the recipient list further comprises determiningcomputing devices with which the user of the computing device has optedinto sharing the information set or data associated with theapplication.
 4. The method of claim 1, further comprising receiving, bythe processor, a deselection of one of the plurality of other computingdevices of the recipient list, such that a deselected one of theplurality of other computing devices is removed from the recipient list.5. The method of claim 1, wherein the information set or the applicationcomprises at least one of a specific document, a word processingapplication, contact information, demographic information, mailingaddress, financial account information, information associated with thecomputing device, or information of another computing device associatedwith the user.
 6. The method of claim 1, the determining of therecipient list and the information set or the application for thepush-based information updates comprises: receiving, by the processor, afirst user input indicating a first plurality of other computing devicesto which changes to a first information set or a first application aretransmitted; and receiving, by the processor, a second user inputindicating a second plurality of other computing devices to whichchanges to a second information set or a second application aretransmitted.
 7. The method of claim 1, wherein the automatic transmit ofthe change comprises transmitting the change directly to the pluralityof other computing devices without being transmitted through anyintermediate communications infrastructure.
 8. The method of claim 1,wherein the computing device is a first computing device associated withthe user, and further wherein at least a second computing device is alsoassociated with the user.
 9. The method of claim 8, wherein the changeto the information set or the application is also transmitted to thesecond computing device.
 10. A system comprising: a memory; a display;and at least one processor of a computing device that is coupled to thememory, the at least one processor configured to: receive user profileconfiguration information identifying a first user; determine arecipient list for push-based information updates, wherein the recipientlist comprises a plurality of other computing devices that are eachassociated with a plurality of users other than the first user, and therecipient list is associated with the user profile configurationinformation; determine an information set or application for thepush-based information updates; receive an input comprising a change tothe information set or the application; and run a daemon process as abackground process of an operating system of the computing device,wherein the daemon process is configured to monitor the information setor the application for changes and automatically transmit the change tothe information set or the application upon the receiving of the inputcomprising the change to the information set or the application, whereinthe change is transmitted to the plurality of other computing deviceswithout receiving a request for the change from any of the plurality ofcomputing devices.
 11. The system of claim 10, wherein the automatictransmit of the change comprises transmitting the change to theplurality of other computing devices via a non-internet connectedcommunications infrastructure.
 12. The system of claim 10, wherein theautomatic transmit of the change comprises transmitting the change tothe plurality of other computing devices via a satellite as acommunications relay.
 13. The system of claim 10, wherein the automatictransmit of the change is configured to be transmitted over internetinfrastructure, but is never received at or re-transmitted by anintermediate server associated with the information set or theapplication.
 14. The system of claim 13, wherein the change to theinformation set or the application is transmitted to the plurality ofother computing devices without a handshake process occurring betweenthe computing device and any of the plurality of other computingdevices.
 15. The system of claim 13, further comprising: receiving, bythe at least one processor, a request to be removed from the recipientlist from one of the plurality of other computing devices of therecipient list comprising; and removing, by the at least one processor,the one of the plurality of other computing devices from the recipientlist.
 16. A non-transitory computer readable medium having instructionsstored thereon that, upon execution by a computing device, cause thecomputing device to perform operations comprising: receiving userprofile configuration information identifying a user; determining arecipient computing device for push-based information updates based onthe user profile configuration information, wherein the recipientcomputing device is associated with a financial institution with whichthe user has an account and the computing device is not accessible bythe user; determining transaction details of a transaction that hasoccurred related to the account; and running a daemon process as abackground process of an operating system of the computing device,wherein the daemon process is configured to monitor the computing devicefor transactions that occur and automatically transmit the transactiondetails directly to the recipient computing device without beingreceived by any intermediate devices so as to push the transactiondetails upon the determining that the transaction has occurred, whereinthe transaction details comprise information configured for verificationof the transaction by the financial institution, and wherein thetransaction details are sent to the recipient computing device withoutreceiving a request for the transaction details from the recipientcomputing device.
 17. The non-transitory computer readable medium ofclaim 16, wherein the transaction details comprise at least one of atransaction amount, a payment method, a merchant name, a timestamp,whether a purchase was in-store or online, or geographic locationinformation of the computing device at a time of the transaction. 18.The non-transitory computer readable medium of claim 16, wherein theinstructions further cause the computing device to perform operationscomprising transmitting, to a payment processing device, information forproviding payment for the transaction, and wherein the transactiondetails comprise identifying information associated with the computingdevice.
 19. The non-transitory computer readable medium of claim 18,wherein the payment processing device is physically proximate to thecomputing device when the information for providing payment for thetransaction is transmitted to the payment processing device, and furtherwherein the recipient computing device is physically remote from boththe payment processing device and the computing device at a time of thetransaction.
 20. The non-transitory computer readable medium of claim16, wherein the transaction details are configured to be compared toinformation about the transaction provided by a payment processor ormerchant for fraud prevention.